The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		May 5, 2026 8:16pm

PR Summary

Medium Risk
Adds cross-cutting analytics correlation by deriving/injecting request_id from both SSE traceparent headers and server request context, which could subtly affect event payloads across the app if parsing or context propagation is wrong.

Overview
Adds request_id correlation across client and server PostHog events to tie task actions to backend logs.

On the client, useChat now extracts a W3C trace ID from the initial chat response traceparent header, exposes it via getCurrentRequestId(), and fires a new task_request_started event; both Home (mothership) and Workflow Copilot views include this ID when emitting task_generation_aborted.

On the server, captureServerEvent auto-injects a request_id from AsyncLocalStorage request context when the caller didn’t already provide one, and the PostHog event map is updated to type the new event and optional request_id fields.

^{Reviewed by Cursor Bugbot for commit 1ed9f52. Configure here.}

Greptile Summary

This PR wires PostHog event correlation for Sim's AI task features by extracting the W3C trace ID from the traceparent response header and emitting it as task_request_started, and by injecting the server-side AsyncLocalStorage request_id automatically into all captureServerEvent calls.

• Adds task_request_started client event (mothership + copilot views) fired when the traceparent response header arrives, capturing the 32-hex W3C trace ID and user_message_id for cross-event join.
• Exposes getCurrentRequestId() from useChat, deriving the trace ID from streamTraceparentRef so task_generation_aborted can carry the same ID as the paired task_request_started.
• Extends captureServerEvent to auto-inject request_id from AsyncLocalStorage context with caller-supplied values taking precedence.

Confidence Score: 5/5

Safe to merge — all changes are additive telemetry instrumentation with no impact on existing chat or streaming logic.

The trace ID extraction uses a consistent path in both onRequestStarted and getCurrentRequestId (same streamTraceparentRef → split('-')[1] → 32-hex regex). The server-side injection correctly guards against overriding caller-supplied request_id. The onRequestStarted callback is wrapped in try/catch. The abort handler reads the ref before invoking stopGeneration(), so clearActiveTurn() cannot race and clear it first. No streaming, auth, or data-path logic is altered.

No files require special attention.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Client
    participant useChat
    participant Server
    participant PostHog

    Client->>Server: POST /api/mothership/chat (userMessageId)
    Server-->>Client: HTTP 200, traceparent: 00-{traceId}-{parentId}-01

    useChat->>useChat: store traceparent in streamTraceparentRef
    useChat->>useChat: extract traceId = traceparent.split('-')[1]
    useChat->>Client: onRequestStarted({ requestId: traceId, userMessageId })
    Client->>PostHog: captureEvent('task_request_started', { request_id: traceId, user_message_id })

    Note over Server,PostHog: Server-side events auto-inject request_id from AsyncLocalStorage
    Server->>PostHog: captureServerEvent(any_event) → auto-injects request_id if absent

    alt User aborts generation
        Client->>useChat: stopGeneration()
        useChat->>useChat: getCurrentRequestId() reads streamTraceparentRef
        Client->>PostHog: captureEvent('task_generation_aborted', { request_id: traceId })
        useChat->>Server: abort stream
        useChat->>useChat: clearActiveTurn() → streamTraceparentRef = undefined
    end

_{Reviews (2): Last reviewed commit: "fix(posthog): use traceparent header as ..." | Re-trigger Greptile}

@greptile

@cursor review